More Pages: Hawkins Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24


"What a delightful book!"
"Thought provoking and inspiring."
"Truly exciting business principles"

A wonderful book
Dolls' House Needlecrafts
questions from Belgium

Wonderful BiographySurprisingly I was also intigued by the book, found the illustrations magnificent and the story "stranger than fiction". Kudos!
MarvelousBeverly J Scott author of Righteous Revenge
Dinosaur Delight and Much, Much More.....

Wake Up Call
Good for the Soul Searcher
Just What I Needed !

Most helpful book I've ever read
School-Savvy is not just for August and September
THIS BOOK IS ESSENTIAL FOR ALL PARENTS OF SCHOOL-AGE CHILDRE

Bad ... vampire novel
You have GOT to buy this book..
wow...

On the short list of great sports booksMore because "Foul" recounts in detail the circumstances that led to Hawkins' longstanding ban from the NBA for his at best highly tenuous link to corruption in college sports. In telling the story, Wolf paints a damning picture of big-time sports, a picture that is, if anything, truer than ever today.
Wolf sets up the story by giving us a glimpse into Hawkins' poverty-stricken childhood in Bedford-Stuyvesant, where he led an unhappy existence that was relieved only when he discovered he had nearly unparalleled basketball skills. He quickly became a playground legend and developed the trademark swooping moves that many of us who got to see him play remember and that made his nickname so apt: Hawk.
Unfortunately, Hawkins did not receive one important thing along the way: an education. One of the most highly recruited players of the time, he was ready to play the college game on the court, but woefully unprepared to play it in the classroom. He was chronically broke, painfully shy, and extremely naive, a combination which made him particularly vulnerable to the unscrupulous character whose actions ultimately led to his ban from the NBA.
"Foul" also tells a detailed and fascinating story of the fledgling American Basketball Association, which was where Hawkins was forced to play and also where he began cementing his legend in the basketball world. It's instructive to read about the low pay and inferior playing conditions Hawkins endured, all the time knowing, of course, that he could easily compete with the best the NBA had to offer.
Finally, the book delivers a detailed account of the legal fight undertaken to remove the ban. This was achieved by his committed -- and of course poorly paid -- attorneys over the determined opposition of, among others, current NBA commissioner David Stern, who hardly expresses remorse in his interviews with the author.
The final sadness of Hawkins' story, of course, is that while he had an above-average NBA career, his best years were taken from him, and most basketball fans were deprived of seeing him when he was one of the best players in the game.
Connie Hawkins remains in my mind after reading this book, not only because of his compelling story, but because of his resilience and humanity. All in all, "Foul" is a sports classic because it fascinates on so many levels.
my grandpa is Scotty McDonald
I red the Chinese version,it is a great book.

Excellent book--great stories, great insights!
This book is wonderful--a must-read!!!
my american adventure

Personal Experience
This way to Enlightenment.
This book will change you foreverThis book is best taken daily; read a paragraph or a sentence, then reflect upon it. Being that it is like "mainlining" spirituality it is practically impossible to take in more that a bit at a time without going into overload.
The benifits of carefully reading and reflecting on this book over time *cannot*, i repeat *cannot* be overestimated, cannot even adequately be put into words.
This book is a perfect complement to "The Power of Now" as well; I found that working with both books simultaneously has a powerful synergistic effect. Tolle is a bit more gentle and hands-on, while Hawkins hits you (lovingly) with a 60ton anvil-over-the-head of direct spiritual truth.


Solid Overview Reference for Project Managers & Analysts
Great introduction for technical and non-technical readersThe authors start by showing how data warehouses fit into the context of IT architecture, and how this relates to fulfilling business needs. This is followed by a clearly presented section on concepts that will be easily understood by non-technical readers, especially business process owner who are exploring the benefits and advantages of data warehousing.
Scope and complexity of designing, implementing and deploying a data warehouse are discussed in detail in Section II, starting with some excellent material for developing a business case and determining the cost/benefit ratio of a data warehouse initiative. Information in this section is also useful for planning a data warehouse project because it provides low-level details on roles and responsibilities. A key point here is the way the project is structured with both technical and business resources. I like this approach because it involves all of the major stakeholders and IT customers from the beginning instead of the more common practice of waiting until the last minute to involve the business. This approach will go a long way towards making a data warehouse project a success and ensuring that the business gets what it really needs instead of what IT thinks the business needs.
The technology section of this book is an excellent description of data structures, meta data and topics that need to be understood in view of the large difference between a data warehouse and an online transaction processing system. I learned a lot from this section and appreciated the way the information was clearly presented. I also liked the fact that the authors included a section on production and maintenance. Other books stop short of this important milestone in a development life cycle, which leaves a lot of unaccounted for issues. This section completes the total picture of a data warehousing initiative and sets realistic expectations for the true costs, resources and effort required to implement and maintain a data warehouse throughout its entire life cycle.
This is a nicely done book that is accessible to both technical and non-technical readers, and is one of the best resources with which to get up-to-speed on data warehousing without getting bogged down with too many technical details.
Good coverages of basics - for managers and non DBAsThis book will give you a solid foundation of the basics, expose the issues and provide a high-level process for planning and implementing a data warehouse. It is divided into sections, the first three covering people, process and technology.
Section One starts with an overview enterprise IT architectures, how data warehousing fits into the scheme of things, and associated business and technical perspectives. I like the way the authors emphasize business perspectives, which is a consistent thread throughout the book. They use a framework called "InfoMotion", which covers all of the requirements, but (to me) is too wrapped-up in "consultant-speak". For example, they litter this section with nonsense such as "InfoMotion = Information/Data * motion. While it makes perfect sense from a conceptual viewpoint, there is no way to compute it, so why express it as a formula? Parenthetically, data is easy to quantify; measuring information is difficult, but can be done. The motion part of the equation is plain silliness because there is no basis given for measurement. But I am nitpicking here.
You are next introduced to data warehouse concepts. This gives a foundation that is complete and covers all key elements, such as reports, definitions of data warehouse and data mart and operational data stores. I thought this was an excellent introduction. Also included is a brief piece on cost/benefit and return on investment. It was short and hit all of the key points, but would have fit better in the prior discussion of the business perspective.
The next section addresses the people part of a data warehousing project, begining with the project sponsor. Answers to some incisive questions are given in this part, such as "how will the data warehouse affect decision-making processes?", "how will it improve financial, marketing and operations processes?" and similar business-focused questions. These draw your attention to the real reasons for data warehousing. This section moves naturally into project management considerations, and exposes some common problems like defining project scope, underestimating time and project overhead or factoring the operational support issues after the data warehouse is rolled out and in production. One of the best parts of this section is how the authors counter common problems and risks with advice on how to eliminate or mitigate them. I liked the approach to measuring results, which gives some sound key performance indications that you can use to baseline some total cost of ownership drivers after the data warehouse is in production. This section continues with roles and responsibilities of the project team. The authors have crafted a sound team structure that consists of business and technical representatives who are overseen by a steering committee. This is an excellent approach. I thought the inclusion of users from various business domains was one of the key strengths, because these people know the data's value to the business a lot better than the technical side of the team. On the other hand, I thought it was naive of the authors to state that this group would be required 80% of the time during the project. While I fully agree with this estimate, it is nearly impossible in practice. I wish the authors would have shared how they sold the business side on making an 80% commitment of their best and brightest.
As this section moves into the actual project there are some things I loved about their approach: breaking the project into four parallel tracks and the proposed rollout strategy. These give you a good understanding of the scope and magnitude of a typical data warehouse project.
Section 4 covers technology, and gets a little too technical for a business user in some places, but is just right for an IT manager who is not a DBA or data architect. I liked the discussion of metadata, why normalization is not appropriate for data warehousing, and the treatment of fact and dimension tables.
The final section discusses maintenance requirements once the data warehouse is in production. This prepares you for the realities of managing these systems. I wish the authors would have addressed some of the workload and scheduling issues that are a part of the territory - refreshing the warehouse is going to require a fine balancing act that is going to affect maintenance windows, other production jobs and a plethora of other production headaches if not planned for in advance.
Overall this is a good book for the audience I cited above. I strongly recommend anyone considering a data warehouse to also read Improving Data Warehouse and Business Information Quality by Larry P. English.